Mobile communication system, base station, CoMP control apparatus and communication control method

ABSTRACT

A mobile communication system includes a first base station, a second base station connected with the first base station via an X2 interface, and a user terminal configured to receive data from both the first and second base stations using radio resources provided by both the first and second base stations. The first base station comprises a controller including at least one processor, the controller executing functions of plural layers. The plural layers include a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer. The controller is configured to receive user data addressed to the user terminal from a core network, convert the user data to PDCP data unit provided with a sequence number, in the PDCP layer, and transmit the PDCP data unit to the second base station from the PDCP layer.

RELATED APPLICATION

The present application is a continuation of U.S. patent applicationSer. No. 14/373,316, filed Jul. 18, 2014, which is a National Phase ofInternational Application Number PCT/JP2013/051004 filed on Jan. 18,2013, and claims priority of U.S. Provisional Application Nos.61/588,502 filed Jan. 19, 2012 and 61/598,782 filed on Feb. 14, 2012.The entire disclosure of U.S. patent application Ser. No. 14/373,316,filed Jul. 18, 2014, is incorporated by reference herein.

TECHNICAL FIELD

The present disclosure relates to a mobile communication system, a basestation, a CoMP control apparatus, and a communication control method,which support CoMP.

BACKGROUND ART

The 3GPP (3rd Generation Partnership Project) which is a mobilecommunication system standardization project is planning to promote thestandardization of CoMP (Coordinated Multi-Point) in the release 11 orlater (see, 3GPP TR 36.819 V11.0.0 (2011-09)).

In the CoMP, a group of antennas installed in the same place is regardedas a “point,” and multiple points cooperatively perform communicationwith a user terminal. The group of points performing cooperativecommunication with the user terminal using one time-frequency resourceis referred to as a CoMP cooperating set.

As one kind of CoMP, there is a JP (Joint Processing) that is a schemein which multiple points in the CoMP cooperating set can use data to becommunicated to the user terminal.

Also, as one kind of JPs in the downlink, there is a JT (JointTransmission) in which multiple points in the CoMP cooperating settransmit data to the user terminal at the same time.

SUMMARY

In some embodiments, a mobile communication system comprises a firstbase station, a second base station connected with the first basestation via an X2 interface, and a user terminal configured to receivedata from both the first and second base stations using radio resourcesprovided by both the first and second base stations. The first basestation comprises a controller including at least one processor, thecontroller executing functions of plural layers. The plural layersinclude a packet data convergence protocol (PDCP) layer, a radio linkcontrol (RLC) layer, a medium access control (MAC) layer, and a physical(PHY) layer. The controller is configured to receive user data addressedto the user terminal from a core network, convert the user data to PDCPdata unit provided with a sequence number, in the PDCP layer, andtransmit the PDCP data unit to the second base station from the PDCPlayer.

In some embodiments, a first base station is connected with a secondbase station via an X2 interface, and comprises a controller includingat least one processor and configured to communicate with a userterminal. The user terminal receives data from both the first and secondbase stations using radio resources provided by both the first andsecond base stations. The controller is configured to execute functionsof plural layers including a packet data convergence protocol (PDCP)layer, a radio link control (RLC) layer, a medium access control (MAC)layer, and a physical (PHY) layer. The controller is further configuredto receive user data addressed to the user terminal from a core network,convert the user data to PDCP data unit provided with a sequence number,in the PDCP layer, and transmit the PDCP data unit to the second basestation from the PDCP layer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a configuration of an LTE system.

FIG. 2 illustrates a configuration of a radio frame used in the LTEsystem.

FIG. 3 illustrates a radio interface protocol in a user plane.

FIG. 4 illustrates a radio interface protocol in a control plane.

FIG. 5 illustrates each layer processing using a downlink as an example.

FIG. 6 illustrates data flow in each layer.

FIG. 7 is a drawing for illustrating a timing advance value.

FIG. 8 is a time chart for illustrating a timing advance value.

FIG. 9 is a block diagram of UE.

FIG. 10 is a block diagram of eNB.

FIG. 11 is a drawing for illustrating a JT-type CoMP.

FIG. 12 is a drawing for illustrating a JR-type CoMP.

FIG. 13 illustrates a control flow of start, continuation, andtermination of CoMP communication.

FIG. 14 illustrates a setting operation flow of a CoMP cooperating set.

FIG. 15 is an X2 measurement message.

FIG. 16 illustrates an example of CoMP cooperating set information.

FIG. 17 illustrates an anchor eNB switch sequence.

FIG. 18 illustrates pattern 1 of an eNB adding sequence.

FIG. 19 illustrates pattern 2 of an eNB adding sequence.

FIG. 20 illustrates a downlink sub-frame configuration.

FIG. 21 illustrates a state where each eNB included in a CoMPcooperating set notifies the other eNBs of an allocation candidate bandin a mutual manner.

FIG. 22 illustrates an example of band allocation information.

FIG. 23 illustrates an example of band allocation processing.

FIG. 24 illustrates an example of band allocation processing.

FIG. 25 illustrates a JT-type CoMP sequence.

FIG. 26 illustrates a JT-type CoMP sequence.

FIG. 27 illustrates a JR-type CoMP sequence.

FIG. 28 illustrates a JT-type CoMP sequence.

FIG. 29 illustrates a sequence in a case where HARQ retransmission doesnot complete even when it reaches the maximum retransmission number.

FIG. 30 is a drawing for illustrating the HARQ retransmission in a MAClayer.

FIG. 31 illustrates a JT-type CoMP sequence.

DESCRIPTION OF THE EMBODIMENT

Embodiments of the present disclosure are described below by referringto the drawings. A mobile communication system according to the presentembodiment is configured based on the 3GPP standards in Release 10 orlater (i.e., LTE Advanced).

Hereinafter, the description is given in the following order of (1)Outline of Embodiments, (2) Outline of LTE System, (3) Configurations ofUE and eNB, (4) Outline of CoMP, (5) Overall Control Flow, (6) CoMPCooperating Set, (7) CoMP Communication Control, and (8) OtherEmbodiments.

(1) Outline of Embodiment

In a mobile communication system according to the present embodiment, aCoMP cooperating set and a UE perform communication therebetween. TheCoMP cooperating set includes an anchor eNB controlling the CoMPcommunication with the UE. The anchor eNB includes a receiver thatreceives user data addressed from an EPC to the UE; a conversion unitthat converts the user data received by the receiver to a PDCP data unitto which a sequence number is added in a PDCP layer; and a transmissionunit that transmits the PDCP data unit obtained by the conversion unitto another eNB included in the CoMP cooperating set.

Also, in a mobile communication system according to the presentembodiment, a CoMP cooperating set performs downlink CoMP communicationwith a user terminal. The CoMP cooperating set includes a main basestation and at least a subordinate base station. The subordinate basestation comprises a transmission unit that performs HARQ datatransmission to the user terminal; and a notification unit that notifiesthe main base station of a failure of the HARQ data transmission whenthe HARQ data transmission fails. The main base station comprises amanagement unit that collectively manages ARQ retransmission data fromthe CoMP cooperating set to the user terminal; a receiver that receivesa notification of the failure of the HARQ data transmission from thesubordinate base station; and a transfer unit that transfers the ARQretransmission data which is managed by the management unit to thesubordinate base station in response to the notification received by thereceiver.

(2) Outline of LTE System

An outline of the LTE system is described in the following order of(2.1) Entire Configuration of LTE System, (2.2) Frame Configuration andPhysical Channel Configuration, (2.3) Protocol Stack, and (2.4) TimingAdvance.

(2.1) Entire Configuration of LTE System

FIG. 1 illustrates a configuration of an LTE system 1.

As depicted in FIG. 1, the LTE system 1, UE (User Equipment), E-UTRAN(Evolved-UMTS Terrestrial Radio Access Network), and EPC (Evolved PacketCore).

The UE is a mobile radio communication apparatus and is equivalent to auser terminal.

The E-UTRAN includes a plurality of eNBs (evolved Node-B). The eNB is astationary radio communication apparatus performing radio communicationwith UE and is equivalent to a base station. Each eNB forms one or moreof cells. The eNB has, for example, a radio resource management (RRM)function, a user data routing function and a measurement controlfunction for mobility control and scheduling.

The EPC includes an MME (Mobility Management Entity) and an S-GW(Serving-Gateway). The EPC is equivalent to a core network. The MME is anetwork entity performing various kinds of mobility control on the UEand is equivalent to a control station. The S-GW is a network entityperforming user data transferring control and is equivalent to anexchange.

The eNBs are connected with one another through an X2 interface. Also,the eNB is connected with the MME and the S-GW through an S1 interface.

(2.2) Frame Configuration and Physical Channel Configuration

FIG. 2 illustrates a configuration of a radio frame which is used in theLTE system 1. The LTE system 1 employs OFDMA (Orthogonal FrequencyDivision Multiplexing Access) for a downlink and SC-FDMA (Single CarrierFrequency Division Multiple Access) for an uplink.

As depicted in FIG. 2, the radio frame includes 10 sub-frames arrangedin a time direction and each sub-frame includes two slots arranged inthe time direction. Each sub-frame has a length of 1 ms and each slothas a length of 0.5 ms. Each sub-frame includes a plurality of resourceblocks (RB) in a frequency direction and a plurality of symbols in thetime direction. A guard section which is called as a cyclic prefix (CP)is provided in the head of each symbol.

(2.2.1) Downlink

In the downlink, a section including a several symbols from the head ofeach sub-frame (specifically, up to 3 or 4 symbols) is a control domainwhich is mainly used as physical downlink control channel (PDCCH). Also,the remaining section of each sub-frame is a data domain which is mainlyused as physical downlink shared channel (PDSCH).

The PDCCH transmits a control signal. The control signal is, forexample, uplink SI (Scheduling Information), downlink SI, and TPC bit.The uplink SI indicates allocation of uplink radio resources and thedownlink SI indicates allocation of downlink radio resources. The TPCbit is a signal instructing increase or decrease of uplink powertransmission. These control signals are referred to as downlink controlinformation (DCI).

The PDSCH carries control signals and/or user data. For example, thedownlink data domain may be allocated only to the user data or may beallocated in such a manner that user data and control signals aremultiplexed.

Note that the control signal which is transmitted via PDSCH includes atiming advance value. The timing advance value is a transmission timingcorrection value of UE and is determined by an eNB based on the uplinksignal which is transmitted from the UE. The timing advance value isdescribed later in detail.

Also, an acknowledgement response (ACK)/a negative acknowledgementresponse (NACK) are carried via a physical HARQ indicator channel(PHICH). The ACK/NACK indicates whether a signal transmitted via anuplink physical channel (for example, PUSCH) is successfully decoded.

(2.2.2) Uplink

In the uplink, both end portions in the frequency direction in eachsub-frame are control domains which are mainly used as physical uplinkcontrol channel (PUCCH). Also, a center portion in the frequencydirection of each sub-frame is a data domain which is mainly used asphysical uplink shared channel (PUSCH).

The PUCCH carries a control signal. The control signal is, for example,CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI(Rank Indicator), SR (Scheduling Request), or ACK/NACK.

The CQI indicates a downlink channel quality and is used for determininga recommendable modulation scheme, coding rate and the like to be usedfor downlink transmission. The PMI indicates a precoding matrix which isdesirable to be used for downlink transmission. The RI indicates thenumber of layers (the number of streams) which can be used for downlinktransmission. The SR is a signal for requesting allocation of an uplinkradio resource (resource block). The ACK/NACK indicates whether or not asignal transmitted via a downlink physical channel (for example, PDSCH)is successfully decoded.

The PUSCH is a physical channel which carries control signals and/oruser data. For example, the uplink data domain may be allocated only tothe user data or may be allocated in such a manner that user data andcontrol signals are multiplexed.

(2.3) Protocol Stack

FIG. 3 illustrates a radio interface protocol in a user plane, and FIG.4 illustrates a radio interface protocol in a control plane. The userplane is a protocol stack for user data transmission and the controlplane is a protocol stack for control signal transmission. FIG. 5illustrates each layer processing using a downlink as an example. FIG. 6illustrates data flow in each layer.

The radio interface protocol is divided into layers 1 to layer 3 in theOSI reference model. The layer 1 is a physical (PHY) layer. The layer 2includes MAC (Media Access Control) layer, RLC (Radio Link Control)layer, and PDCP (Packet Data Convergence Protocol) layer. The layer 3includes RRC (Radio Resource Control) layer.

The physical layers perform data coding-decoding,modulation-demodulation, antenna mapping-demapping and resourcemapping-demapping. The physical layer provides transmission service toan upper layer using the above-described physical channel. Data istransmitted via the physical channel between the physical layer of UEand the physical layer of the eNB. The physical layer is connected witha MAC layer via a transport channel.

The MAC layer performs priority control of data and retransmissionprocessing or the like through hybrid ARQ (HARM). Data is transmittedvia the transport channel between the MAC layer of UE and the MAC layerof the eNB. Also, the MAC layer performs mapping between a logicalchannel and a transport channel. The MAC layer of the eNB includes anuplink transport format and a MAC scheduler determining a resourceblock. The transport format contains a transport block size,modulation-coding scheme (MAC) and antenna mapping. The MAC layer isconnected with the RLC layer via the logical channel.

The RLC layer receives data from a PDCP layer in the form of RLC SDU(Service Data Unit). Data is transmitted via a logical channel betweenthe RLC layer of UE and the RCL layer of the eNB. The RLC layertransmits date to the RLC layer on the receiver side using functions ofthe MAC layer and the physical layer. Note that PDU in the upper layercorresponds to SDU in the lower layer. For this reason, the RLC SDU issometimes referred to as PDCP PDU (Protocol Data Unit). An RLC PDUlength changes along with a situation of transmission rate optimizationand a dynamic scheduling. For this reason, a payload length to betransmitted in a sub-frame can be changed. Thus, the RLC layer dividesand couples RLC SDU (PDCP PDU) according to the RLC PDU length.

The RCL layer includes three modes. Specifically, the RCL layer operatesin any of a transparent mode (TM), unacknowledgement response mode (UM),and acknowledgement response mode (AM), in response to a request from anapplication. In the TM mode, the RLC layer is bypassed. In the UM mode,data division and coupling are performed but ARQ retransmission is notperformed. In the AM mode, not only data division and assembly areperformed but also ARQ retransmission is performed in case of RLC PDUtransmission failure. Higher reliability can be obtained by performingboth HARQ in the MAC layer and ARQ in the RLC layer.

The RLC layer is connected with a PDCP layer via a radio bearer.

The PDCP layer performs header compression and decompression andperforms encryption and decoding. The header compression reduces an IPpacket header size containing unnecessary control information. Data istransmitted via the radio bearer between the PDCP layer of UE and thePDCP layer of the eNB.

The RRC layer is defined only in the control plane. The RRC layercontrols a logical channel, a transport channel, and a physical channelaccording to establishment, reestablishment and release of the radiobearer. When RRC connection is present between RRC of the UE and RRC ofthe eNB, the UE is in the RRC connected state, and if not, the UE is inthe RRC Idle state.

An NAS (Non-Access Stratum) layer located in an upper layer of the RRCperforms session management and mobility management.

(2.4) Timing Advance

In the uplink, UE being located far from an eNB needs to advance datatransmission timing so as to be timed with reception timing of eNB. Forthis reason, the eNB measures timing of an uplink signal received fromUE, creates a timing advance value for adjusting (correcting) datatransmission timing of UE, and then, notifies the UE of the timingadvance value as TA MCE (Timing Advance Command Mac Control Element).

The timing advance value is an offset value of timing at which UE startstransmission with respect to the current transmission timing of UE.Since the UE may move, the eNB updates the timing advance valueregularly and transmits the timing advance value to the UE.

Also, if the UE transmits nothing for a certain period of time, thetiming advance value for the UE becomes uncertain. Accordingly, in orderto avoid unadjusted UE transmission, both the eNB and the UE include atimer (“Time Alignment Timer”) for determining a valid period of atiming advance value, and determine whether the UE is out ofsynchronization in the uplink.

FIG. 7 and FIG. 8 are drawings for illustrating a timing advance value.FIG. 7 and FIG. 8 depict a situation where UE moves.

As illustrated in FIG. 7, in the situation where UE approaching eNB, theeNB creates a negative offset value as a timing advance value withrespect to the current transmission timing of the UE so as to delay thetransmission timing of the UE. Then, the eNB notifies the UE of thetiming advance value (TA MCE). When receiving the timing advance value(TA MCE), the UE delays the transmission timing according to the timingadvance value (TA MCE).

As illustrated in FIG. 8, in the situation where UE is moving away fromeNB, the eNB creates a positive offset value as a timing advance valuewith respect to the current transmission timing of the UE so as toadvance the transmission timing of the UE. Then, the eNB notifies the UEof the timing advance value (TA MCE). When receiving the timing advancevalue (TA MCE), the UE advances the transmission timing according to thetiming advance value (TA MCE).

(3) Configurations of UE and eNB

Hereinafter, the description is given to (3.1) Configuration of UE and(3.2) Configuration of eNB

(3.1) Configuration of UE

FIG. 9 is a block diagram of UE.

As shown in FIG. 9, UE has an antenna 110, a radio transceiver 120, anda controller 130. The UE may further have a user interface and abattery.

The antenna 110 and the radio transceiver 120 are used for transmissionand reception of a radio signal.

The controller 130 performs processing in each of the above-describedlayers. The controller 130 includes a processor 131 and a memory 132.The processor 131 performs processing in each of the layers by executinga program stored in the memory 132.

Also, the processor 131 performs control in the UE regarding CoMPcommunication (the detail is described later). The memory 132 storesinformation to be used for control in the UE regarding the CoMPcommunication.

(3.2) Configuration of eNB

FIG. 10 is a block diagram of eNB.

As illustrated in FIG. 10, eNB has an antenna 210, a radio transceiver220, a network communication unit 230, and a controller 240.

The antenna 210 and the radio transceiver 220 are used for transmissionand reception of a radio signal. The network communication unit 230performs communication on an X2 interface and an S1 interface.

The controller 240 performs processing in each of the above-describedlayers. The controller 240 includes a processor 241 and a memory 242.The processor 241 performs processing in each of the layers by executinga program stored in the memory 242.

Also, the processor 241 performs control in the eNB regarding CoMPcommunication (the detail is described later). The memory 242 storesinformation to be used for control in the eNB regarding the CoMPcommunication.

(4) Outline of CoMP

In CoMP, a group of antennas installed in a same place is regarded as a“point,” and multiple points cooperatively perform communication withUE. The group of points performing cooperative communication with UE isreferred to as a CoMP cooperating set.

As one kind of CoMP, there is a JP (Joint Processing) which is a schemein which data to be communicated with UE can be used in multiple pointsin the CoMP cooperating set. As one kind of JPs in the downlink, thereis a JT (Joint Transmission) in which multiple points in the CoMPcooperating set transmit data to UE at the same time. As one kind of JPsin the uplink, there is a JR (Joint Reception) in which multiple pointsin the CoMP cooperating set receive same data from UE.

In addition, there is DCS (Dynamic Cell Selection) which is one kind ofJPs in the downlink and in which only one point having the best radiostate performs transmission. Also, there is CS (Coordinated Scheduling)in which only one point holds data regarding each of the uplink and thedownlink while multiple points cooperatively perform scheduling/resourceallocation. Furthermore, there is CB (Coordinated Beamforming) in whichonly one point holds data regarding mainly the downlink while multiplepoints cooperatively perform beamforming.

Hereinafter, the description is given to a case where eNBs operate aspoints in the CoMP cooperating set and perform JP-type (JT, JR) CoMP.

FIG. 11 is a drawing for illustrating a JT-type CoMP. In FIG. 11, the UE100 is located in a coverage area edge portion (i.e., a boundary region)of each eNB.

As illustrated in FIG. 11, the CoMP cooperating set includes eNB 200 toeNB 204. The eNB 200 is an anchor eNB which receives data addressed fromS-GW to the UE 100, on behalf of the eNB 200 to the eNB 204. The anchoreNB 200 is equivalent to a main base station which performs control ofdownlink CoMP communication. Also, the anchor eNB 200 is equivalent to aCoMP management apparatus which manages a CoMP cooperating set. Theother eNBs (eNB 201 to eNB 204) are equivalent to subordinate basestations.

First, the anchor eNB 200 receives data from S-GW and transfers data tothe eNB 201 to the eNB 204 over the X2 interface.

Second, each of the eNB 200 to the eNB 204 transmits data to the UE 100on a radio interface using a same communication resource (sametime-frequency resource and same MCS).

Third, the UE 100 receives data transmitted from the eNB 200 to the eNB204. As described above, when the UE 100 is located in the coverage areaedge portion and receives data from the plurality of eNBs through thesame communication resource, a combined gain can be obtained. Thus, acommunication quality is improved.

FIG. 12 is a drawing for illustrating a JR-type CoMP. In FIG. 12, the UE100 is located in a coverage area edge portion (i.e., a boundary region)of each eNB.

As illustrated in FIG. 12, the eNB 200 of the eNB 200 to the eNB 204included in the CoMP cooperating set is an anchor eNB, representing theeNB 200 to the eNB 204, which performs data transmission to EPC(specifically, S-GW). The anchor eNB 200 is equivalent to a main basestation which performs control of uplink CoMP communication. Other eNBs(eNB 201 to eNB 204) are equivalent to subordinate base stations.

First, the UE 100 transmits data on the radio interface using apredetermined communication resource.

Second, each of the eNB 200 to the eNB 204 performs reception with thepredetermined communication resource. Each of the eNB 201 to the eNB 204transfers data from the UE 100 over the X2 interface to the anchor eNB200 in a state of a baseband signal without performing decoding thereceived data (specifically decoding in the physical layer). Note thatthere is also a scheme of transferring data after being decoded inaddition to the scheme of performing transfer in the state of basebandsignal.

Third, the anchor eNB 200 receives data from the eNB 201 to the eNB 204.The anchor eNB 200 decodes the data which is received by itself from theUE 100 and the data which is received from the eNB 201 to the eNB 204after the data is combined. Then, the anchor eNB 200 transfers thedecoded data to the S-GW on the S1 interface.

In this manner, the data which is received by the plurality of eNBs iscombined to obtain a combined gain. Thus, the communication quality isimproved.

Note that, a frequency resource (resource block), a time resource(sub-frame), and modulation scheme (MCS) which are used for the CoMPcommunication are collectively referred to as a “band”.

(5) Overall Control Flow

FIG. 13 illustrates an overall control flow, more specifically, acontrol flow of start, continuation, and termination of CoMPcommunication. The flow is periodically executed by the eNB 200operating as an anchor eNB. However, before starting the CoMPcommunication, the present flow is periodically executed by the eNB 200configuring a serving cell of UE.

As illustrated in FIG. 13, at step S100, the eNB 200 receives aMeasurement Report from the UE 100. The measurement report containsinformation of a signal level (specifically, a power level) of areference signal received by the UE from each eNB (or each cell).

At step S101, the eNB 200 calculates a difference between a signal levelof the eNB 200 and a signal level of another eNB based on themeasurement report received at step S100.

If the CoMP communication is not performed (step S102; No), the eNB 200checks at step S103 if the signal level of the other eNB is higher thanits own signal level and the signal level difference calculated at stepS101 is larger than a threshold Pth0. If the signal level of the othereNB is higher and the signal level difference calculated at step S101 islarger than the threshold Pth0 (step S103; Yes), processing proceeds tostep S109, and if not (step S103; No), processing proceeds to step S104.

At step S109, the eNB 200 starts a handover sequence to the other eNB.Accordingly, the UE 200 performs handover to the other eNB. Note that anexisting specification can be applied to the handover sequence.

On the other hand, at step S104, the eNB 200 checks if the signal leveldifference calculated at step S101 is within a range of a thresholdPth1. Here, the Pth1 is a value smaller than the Pth0. When the signallevel difference calculated at step S101 is within the range of thethreshold Pth1 (step S104; Yes), processing proceeds to step S106, andif not (step S104; No), processing proceeds to step S105.

At step S105, the eNB 200 updates a boundary region residence time to 0.This is because the signal level difference is relatively large if thestep S104 is No, and thus the UE 100 cannot be regarded as being locatedin the boundary region.

Meanwhile, at step S106, the eNB 200 adds 1 to the boundary regionresidence time. Thereafter, processing proceeds to step S107.

At step S107, the eNB 200 checks if the boundary region residence timeexceeds a threshold Tth0. When the boundary region residence timeexceeds the threshold Tth0 (step S107; Yes), processing proceeds to stepS108. When the boundary region residence time exceeds the thresholdTth0, the UE 100 is regarded as staying in the boundary region.

At step S108, the eNB 200 determines that the CoMP communication is tobe started. When the CoMP communication is started, the eNB 200 performssetting processing of the CoMP cooperating set (the detail is describedlater).

On the other hand, when the CoMP communication is being performed (stepS102; Yes), at step S110, the eNB 200 checks if the signal leveldifference calculated at step S101 is within a range of a thresholdPth3. When the signal level difference calculated at step S101 is withinthe range of the threshold Pth3 (step S110; Yes), processing proceeds tostep S114, and if not (step S110; No), processing proceeds to step S111.

At step S114, the eNB 200 determines that the CoMP communication is tobe continued.

Note that the eNB 200 may be added anew to the CoMP cooperating setduring execution of the CoMP communication based on the measurementreport from the UE 100. The details of the eNB adding sequence isdescribed later.

On the other hand, at step S111, the eNB 200 checks if the signal leveldifference calculated at step S101 is within a range of a thresholdPth2. Here, the Pth2 is a value larger than the Pth3. When the signallevel difference calculated at step S101 is within the range of thethreshold Pth2 (step S111; Yes), processing proceeds to step S113, andif not (step S111; No), processing proceeds to step S112.

At step S113, the eNB 200 starts an anchor switch sequence for switchingthe anchor eNB from the eNB 200 to the other eNB. The detail of theanchor switch sequence is described later.

On the other hand, at step S112, the eNB 200 determines that the CoMPcommunication to be terminated and performs processing of terminatingthe CoMP communication

(6) CoMP Cooperating Set

Hereinafter, the CoMP cooperating set is described in the order of (6.1)CoMP Cooperating Set Setting Operation, (6.2) Anchor eNB Switchsequence, and (6.3) eNB Adding Sequence.

(6.1) CoMP Cooperating Set Setting Operation

When the CoMP cooperating set is formed by different eNBs, a band to beallocated to the UE has to be determined by negotiation among the eNBs.If the negotiation takes a long time due to transmission delay among theeNBs (i.e., transmission delay over the X2 interface), dynamic bandallocation cannot be achieved. For this reason, in order to attain thedynamic band allocation, the present embodiment employs the followingconfiguration.

The eNB according to the present embodiment comprises an acquisitionunit (the network communication unit 230 and the processor 241) thatacquires transmission delay between itself and a neighboring eNB and aregistration unit (the processor 241 and the memory 242) that registersthe neighboring eNB as an eNB to be included in the CoMP cooperating setwhen the transmission delay acquired by the acquisition unit is smallerthan a threshold. On the other hand, the registration unit excludes theneighboring eNB from eNBs to be included in the CoMP cooperating setwhen the transmission delay acquired by the acquisition unit is equal toor larger than the threshold.

In addition, even with the intension of forming the CoMP cooperating setby using different eNBs, not all the eNBs support all the CoMP types. Onthe other hand, the eNBs in the CoMP cooperating set have to use acommon type of CoMP. For this reason, in order to easily form the CoMPcooperating set in which a common CoMP type is supported, the presentembodiment employs the following configuration is used.

The eNB according to the present embodiment is an eNB supporting CoMP,and comprises a receiver (the network communication unit 230) thatreceives a notification of CoMP type supported by a neighboring eNB anda storage (the processor 241 and the memory 242) that stores informationof the neighboring eNB in association with the CoMP type supported bythe neighboring eNB based on the notification received by the receiver.

FIG. 14 illustrates a setting operation flow of a CoMP cooperating set.The flow is periodically executed by the eNB 200 operating as an anchoreNB at the time of starting the CoMP communication. However, the flowmay be periodically executed after the CoMP communication is started.FIG. 15 illustrates an X2 measurement message which is used in the flow.

As illustrated in FIG. 14, at step S200, the eNB 200 starts processingloop for each of other neighboring eNBs (neighboring eNB). Theneighboring eNB may be an eNB whose identifier is included in a neighborlist set in the eNB 200 (i.e., a neighboring eNB) or may be an eNBhaving the X2 interface established with the eNB 200.

At step S201, the eNB 200 transmits an X2 measurement message 1 over theX2 interface to a neighboring eNBi (i=0 to n). Here, an initial value of“i” is 0 and 1 is added to each loop. Note that when “i” reaches “n”,the loop is broken.

As illustrated in FIG. 15, the X2 measurement message contains timeinformation (hereinafter, referred to as “time stamp T0”) when the X2measurement message 1 is transmitted.

The neighboring eNBi which has received the X2 measurement message 1transmits an X2 measurement message 2 containing various pieces ofinformation to be described later over the X2 interface.

At step S202, the eNB 200 receives the X2 measurement message 2transmitted from the neighboring eNBi. The eNB 200 acquires timeinformation (hereinafter, referred to as “time stamp T3”) when the X2measurement message 2 is received from the neighboring eNBi.

As illustrated in FIG. 15, the X2 measurement message 2 contains thetime stamp T0 contained in the X2 measurement message received by theneighboring eNBi, time information (hereinafter, referred to as “timestamp T2”) when the neighboring eNBi received the X2 measurement message1, time information (hereinafter, referred to as “time stamp T1”) whenthe neighboring eNBi transmitted the X2 measurement message 2, a type ofdownlink CoMP supported by the neighboring eNBi (hereinafter, referredto as “DL supporting CoMP type”), and a type of uplink CoMP supported bythe neighboring eNBi (hereinafter, referred to as “UL supporting CoMPtype”). FIG. 15 illustrates JT, DCS, CS, CB as types of DL CoMPsupported by the neighboring eNBi. Also, JR and CS are illustrated astypes of UL CoMP supported by the neighboring eNBi.

At step S203, the eNB 200 calculates transmission delay Tsnd in adirection from the eNB 200 to the neighboring eNBi (a transmissionmethod) and transmission delay Trec in a direction from the neighboringeNBi to the eNB 200 (a reception method) based on the above-describedtime stamps T0 to T3. Specifically, the eNB 200 calculates a differencebetween the time stamp T0 contained in the X2 measurement message 2 andthe time stamp T2 contained in the X2 measurement message 2 as thetransmission delay Tsnd. Also, the eNB 200 calculates a differencebetween the time stamp T1 contained in the X2 measurement message 2 andthe time stamp T3 acquired by itself as the transmission delay Trec.

At step S204, the eNB 200 sets a threshold Th according to the CoMP type(i.e., the CoMP type supported by the eNB 200) which is planned to beused by the eNB 200. For example, the JT, JR, DCS belonging to the JPtype require high-speed communication among the respective eNBs includedin the CoMP cooperating set. Accordingly, a threshold Th whose conditionis strict is set. On the other hand, the CS and CB are not forsimultaneously performing transmission or reception by plurality ofeNBs, and thus do not require high-speed communication among the eNBs ascompared with the case of the JP type. Accordingly, in order to increasethe number of eNBs to be included in the CoMP cooperating set, athreshold Th whose condition is lax (i.e., a value larger than thethreshold in the JP type) is set.

At step S205, the eNB 200 compares each of the transmission delay Tsndand the transmission delay Trec calculated at step S203 with thethreshold Th set at step S204. When both the transmission delay Tsnd andthe transmission delay Trec are smaller than the threshold Th (stepS205; Yes), processing proceeds to step S209, and if not, processingproceeds to step S206.

At step S209, the eNB 200 checks if the DL supporting CoMP typecontained in the X2 measurement message 2 indicates “presence” of the DLsupporting CoMP type (i.e., if the neighboring eNBi supports thedownlink CoMP or not). When the neighboring eNBi supports the downlinkCoMP (step S209; Yes), at step S210, the eNB 200 registers theneighboring eNBi as an eNB to be included in the downlink CoMPcooperating set.

Next, at step S211, the eNB 200 checks if the UL supporting CoMP typecontained in the X2 measurement message 2 indicates “presence” of the ULsupporting CoMP type (i.e., if the neighboring eNBi supports the uplinkCoMP or not). When the neighboring eNBi supports the uplink CoMP (stepS211; Yes), at step S212, the eNB 200 registers the neighboring eNBi asan eNB to be included in the uplink CoMP cooperating set.

At step S206, if it is determined that processing for all theneighboring eNBs is terminated, the loop is broken.

At step S207, the eNB 200 transmits CoMP cooperating set information onthe CoMP cooperating set over the X2 interface to each of eNBs to beincluded in the CoMP cooperating set. The eNB having received the CoMPcooperating set information stores the received CoMP cooperating setinformation.

At step S208, the eNB 200 transmits the CoMP cooperating set informationto the UE 100.

Note that although the details are described later, in a case where theeNB included in the CoMP cooperating set is changed (added, excluded oranchor eNB is changed) during the CoMP communication, or in a case wherecommunication setting applied to the CoMP cooperating set is changed,the anchor eNB changes the CoMP cooperating set information andtransmits the changed CoMP cooperating set information over the X2interface. The eNB having received the changed CoMP cooperating setinformation updates the information to the changed CoMP cooperating setinformation.

FIG. 16 illustrates an example of the CoMP cooperating set information.The eNBs and UE performing CoMP communication stores the CoMPcooperating set information on the CoMP communication.

The example of FIG. 16 illustrates the CoMP cooperating set informationon the CoMP cooperating set only performing the uplink CoMPcommunication, the CoMP cooperating set information on the CoMPcooperating set only performing the downlink CoMP communication, and theCoMP cooperating set information on the CoMP cooperating set performingboth the uplink and downlink CoMP communication.

Assumed herein is a case where the eNB only performs the uplink CoMPcommunication with the UE 1, only performs the downlink CoMPcommunication with the UE 2, and performs both the uplink and downlinkCoMP communication with the UE 3.

The CoMP cooperating set information contains C-RNTI (Cell-Radio NetworkTemporary Identity). The C-RNTI is a temporal UE identifier referred toas a cell specific radio network temporal identity. Although the detailsare described later, the C-RNTI may be changed when an eNB is to beadded to the CoMP cooperating set. In this case, the CoMP cooperatingset information contains each C-RNTI before and after the change.

The CoMP cooperating set information contains an eNB identifier (or acell identifier) of each eNB included in the CoMP cooperating set and aneNB identifier (or a cell identifier) of an anchor eNB included in theCoMP cooperating set.

The CoMP cooperating set information contains a downlink HARQ firsttransmission allocation interval and uplink HARQ first transmissionallocation interval. The details of the HARQ first transmissionallocation interval are described later.

The CoMP cooperating set information contains resource block information(e.g., a resource block number) of E-PDCCH (Evolved-PDCCH). The detailsof the E-PDCCH are described later.

The CoMP cooperating set information contains information indicatingtiming allocated to the UE. The expression of “offset (SFN, subframe)”in FIG. 16 means to allocate timing when “Current Time(=SFN*10+subframe) modulo allocation interval”=“offset(=SFN*10+subframe) modulo allocation interval” is fulfilled. Asdescribed above, the eNB 200 acquires the transmission delay betweenitself and the neighboring eNB. When the acquired transmission delay issmaller than a threshold, the neighboring eNB is registered as an eNB tobe included in the CoMP cooperating set. Also, the neighboring eNB isexcluded from eNBs to be included in the CoMP cooperating set when theacquired transmission delay is equal to or larger than the threshold.Accordingly, the neighboring eNB whose transmission delay is large overthe X2 interface can be excluded from eNBs to be included in the CoMPcooperating set. Thus, dynamic band allocation can be achieved.

In the present embodiment, the eNB 200 registers the neighboring eNB asan eNB to be included in the CoMP cooperating set when the transmissiondelay Tsnd in the direction from the eNB 200 to the neighboring eNB (thetransmitting direction) and the transmission delay Trec in the directionfrom the neighboring eNB to the eNB 200 (the receiving direction) areacquired and the both the transmission delay Tsnd and the transmissiondelay Trec are equal to or smaller than the threshold. Accordingly, theCoMP communication can be started after it is checked that the delay issmall in both the transmitting direction and the receiving direction.

In the present embodiment, the eNB 200 sets a threshold to be comparedwith the transmission delay Tsnd and the transmission delay Trecaccording to the CoMP type to be used in the CoMP cooperating set. Arequired transmission delay condition can be met for each CoMP type.

In the present embodiment, the eNB 200 receives the notification of theCoMP type supported by the neighboring eNB and stores the neighboringeNB information based on the received notification in association withthe CoMP type supported by the neighboring eNB. In particular,information pieces on neighboring eNBs supporting a same CoMP type arestored as a group. Accordingly, the eNB 200 can manage neighboring eNBsas groups on the supporting CoMP type basis. Thus, the CoMP cooperatingset in which a common CoMP type is supported can be easily formed.

In the present embodiment, the CoMP cooperating set only performing thedownlink CoMP, the CoMP cooperating set only performing the uplink CoMP,and the CoMP cooperating set performing both the uplink and downlinkCoMP can be individually managed. Thus, one eNB can perform a pluralityof types of CoMP communication. Also, the UE can have different CoMPcooperating sets among the CoMP cooperating set only performing thedownlink CoMP, the CoMP cooperating set performing the uplink CoMP, andthe CoMP cooperating set performing both the uplink and downlink CoMP.

(6.2) Anchor eNB Switch Sequence

Next, the anchor eNB switch sequence is described. In order to followmovement of UE, it is desirable that an anchor eNB is switched as neededamong eNBs included in the CoMP cooperating set. In the presentembodiment, the anchor eNB transmits, to another eNB included in theCoMP cooperating set, an anchor switch request for requesting the othereNB to be a new anchor eNB in the CoMP cooperating set based on ameasurement report from the UE. If accepting the anchor switch requestfrom the anchor eNB, the other eNB is switched to the new anchor eNBafter transmitting positive acknowledgement in response to the anchorswitch request to the anchor eNB, and then. After the other eNB isswitched to the new anchor eNB, the other eNB notifies other eNBsincluded in the CoMP cooperating set that the other eNB itself becomesthe new anchor eNB.

FIG. 17 illustrates an anchor eNB switch sequence. Here, the descriptionis given to an example in which an anchor eNB is switched from the eNB200 to the eNB 201 while the CoMP cooperating set is formed by the eNB200 to the eNB 203 and the UE 100 are executing the JT type CoMP.

As illustrated in FIG. 17, at step S1001, the eNB 200 receives packetdata from the S-GW. Although the details are described later, the eNB200 converts the packet data in the PDCP layer to PDCP PDU and adds asequence number to the PDCP PDU.

At step S1002, the eNB 200 transfers the PDCP PDU to which the sequencenumber is added to the eNB 201 to the eNB 203 over the X2 interface.

At step S1003, each of the eNB 200 to the eNB 203 transmits/receivesband allocation information on an allocation candidate band to/fromanother eNB included in the CoMP cooperating set over the X2 interfaceand determines a band to be allocated to the UE 100. The details of theband allocation information are described later.

At step S1004, each of the eNB 200 to the eNB 203 allocates the banddetermined at step S1003 to the UE 100 and transmits the same data tothe UE 100.

At step S1005, the UE 100 transmits a measurement report. Each of theeNB 200 to the eNB 203 receives the measurement report.

At step S1006, the eNB 200 determines that the anchor eNB is to beswitched to the eNB 201 based on the measurement report.

At step S1007, the eNB 200 transmits an anchor switch request forrequesting the eNB 201 to be a new anchor eNB to the eNB 201 over the X2interface.

At step S1008, the eNB 201 determines that the anchor switch requestfrom the eNB 200 is accepted, and transmits an anchor switch responseindicating that to the eNB 200 over the X2 interface.

At step S1009, the eNB 200 transmits an SN Status transfer messageindicating a state of transmission/reception with the UE 100 to the eNB201 over the X2 interface in order to forward unsent data to the UE 100.

At step S1010, the eNB 200 forwards (forwarding) the data unsent to theUE 100 to the eNB 201 over the X2 interface.

At step S1011, the eNB 201 transmits a path switch request for switchinga data path (path) to the eNB 201 to MME on the S1 interface.

At step S1012, the MME transmits a bearer change request to the S-GW inresponse to the path switch request from the eNB 201. The S-GW startsprocessing of switching the data path from the eNB 200 to the eNB 201 inresponse to the bearer change request from the MME.

At step S1013, the S-GW transmits End Marker indicating that datatransfer to the eNB 200 is terminated to the eNB 200 on the S1interface.

At step S1014, the S-GW transmits packet data to the eNB 201 on the S1interface.

At step S1015, the eNB 200 transmits End Marker indicating that datatransfer (forwarding) to the eNB 201 is terminated to the eNB 201 overthe X2 interface.

At step S1016, the S-GW transmits a bearer changing response which is aresponse to the bearer change request received at step S1012 to the MME.

At step S1017, the MME transmits a path switch response which is aresponse to the path switch request received at step S1011 to the eNB201 on the S1 interface.

At step S1018, the eNB 201 notifies the eNB 200 over the X2 interfacethat the switching of the anchor eNB is completed. After that, the eNB201 operates as a new anchor eNB. The eNB 201 switched to the new anchoreNB updates the CoMP cooperating set information stored in the eNB 201such that the eNB 201 itself is set as the anchor eNB.

At step S1019, the eNB 201 transmits the updated CoMP cooperating setinformation to the eNB 200, the eNB 202, and the eNB 203 over the X2interface. Furthermore, the eNB 201 may notify the UE of the updatedCoMP cooperating set information. The eNB 200, the eNB 202, and the eNB203 store the updated CoMP cooperating set information when the updatedCoMP cooperating set information is received.

At step S1020, the eNB 201 transfers the PDCP PDU obtained after thepacket data received from the S-GW at step S1014 is converted to the eNB200, the eNB 202, and the eNB 203 over the X2 interface.

As described above, the eNB 200 transmits an anchor switch request forrequesting another eNB 201 included in the CoMP cooperating set to be anew anchor eNB in the CoMP cooperating set based on a measurement reportfrom the UE. If accepting the anchor switch request from the eNB 200,the eNB 201 transmits an anchor switch response which is acknowledgementresponding to the anchor switch request to the eNB 200 and then isswitched to a new anchor eNB. Accordingly, the anchor eNB can beswitched without stopping the CoMP communication.

In the present embodiment, after the eNB 201 is switched to a new anchoreNB, the eNB 201 notifies the eNB 200, the eNB 202, and the eNB 203 thatthe eNB 201 is the new anchor eNB. Accordingly, even if an anchor eNB isswitched during the CoMP communication, each eNB included in the CoMPcooperating set can know the new anchor eNB.

(6.3) eNB Adding Sequence

When the CoMP cooperating set is formed by different eNBs, it isdesirable to add a new eNB as needed to the CoMP cooperating set inorder to deal with the movement of the UE. However, assumed is a casewhere the new eNB has already been using the C-RNTI to be used in theCoMP cooperating set. The C-RNTI is needed for controlling radiocommunication with the UE. Since the same C-RNTI cannot be allocated toa plurality of UEs in the same eNB (the same cell), it is difficult toadd the new eNB to the CoMP cooperating set.

For this reason, in the present embodiment, to add a new eNB to the CoMPcooperating set, the anchor eNB transmits, to another eNB which is notincluded in the CoMP cooperating set, a CoMP adding request forrequesting the other eNB to be added to the CoMP cooperating set. Also,when the CoMP adding request is transmitted, the C-RNTI being used forcommunication with the UE is transmitted to the other eNB.

Note that when an eNB is added, it is preferable that the CoMPcooperating set setting operation described in (6.1) be performed, butthe description of the operation is omitted in the following sequence.

(6.3.1) eNB Adding Pattern 1

FIG. 18 illustrates a pattern 1 of an eNB adding sequence. Here, thedescription is given to an example in which the eNB 203 is added to theCoMP cooperating set while the CoMP cooperating set formed by the eNB200 to the eNB 202 and the UE 100 are executing the JT type CoMP. Also,the eNB 203 allocates C-RNTI same as the C-RNTI allocated to the UE 100to the UE connected with the eNB 203.

As illustrated in FIG. 18, at step S2001, the eNB 200 operating as ananchor eNB receives packet data from the S-GW. Although the eNB 200converts the packet data in the PDCP layer to PDCP PDU and adds asequence number to the PDCP PDU.

At step S2002, the eNB 200 transfers the PDCP PDU to which the sequencenumber is added to the eNB 201 and the eNB 202 over the X2 interface.

At step S2003, each of the eNB 200 to the eNB 202 transmits/receivesband allocation information on an allocation candidate band to/fromanother eNB included in the CoMP cooperating set over the X2 interfaceand determines a band to be allocated to the UE 100.

At step S2004, each of the eNB 200 to the eNB 202 allocates the banddetermined at step S2003 to the UE 100 and transmits the same data tothe UE 100.

At step S2005, the UE 100 transmits a measurement report. Each of theeNB 200 to the eNB 202 receives a measurement report.

At step S2006, the eNB 200 determines based on the measurement reportthat the eNB 203 is added to the CoMP cooperating set. For example, theeNB 200 determines that the eNB is added to the CoMP cooperating setwhen the measurement report received at this time contains a signallevel about eNB (cell) which is not contained until the previousmeasurement report and the signal level has a value suitable for theCoMP communication.

At step S2007, the eNB 200 transmits a CoMP adding request forrequesting to be added to the CoMP cooperating set over the X2interface. The eNB 200 transmits C-RNTI which is being used for the CoMPcommunication with the UE 100 with the C-RNTI contained in the CoMPadding request.

At step S2008, the eNB 203 determines based on the CoMP adding requestreceived from the eNB 200 if C-RNTI same as the C-RNTI which is beingused in the CoMP cooperating set to which the eNB 200 belongs is used.Specifically, the eNB 203 determines if the C-RNTI contained in thereceived CoMP adding request meets with any of the C-RNTIs which arebeing used in the eNBs (already allocated). Here, the eNB 203 determinesthat the same C-RNTI is used.

At step S2009, the eNB 203 transmits, to the eNB 200, a CoMP addingresponse which is a response to the CoMP adding request over the X2interface. The eNB 203 transmits information indicating that the sameC-RNTI is being used with the information being contained in the CoMPadding response.

At step S2010, the eNB 200 transmits an unused C-RNTI request forrequesting to notify an unused (not-allocated) C-RNTI of the eNB 201 tothe eNB 203 over the X2 interface in response to the fact thatinformation indicating that the same C-RNTI is being used is containedin the CoMP adding response.

At step S2011, each of the eNB 201 to the eNB 203 extracts C-RNTI whichis unused in the eNB itself in response to the unused C-RNTI request andtransmits the unused C-RNTI response including the C-RNTI unused in theeNB itself to the eNB 200 over the X2 interface.

At step S2012, the eNB 200 selects a common C-RNTI among the C-RNTIunused in the eNB 200 and an unused C-RNTI contained in the unusedC-RNTI response (C-RNTI unused in each of the eNB 201 to the eNB 203)and the selected C-RNTI is determined as a new C-RNTI to be used for theCoMP communication with the UE 100.

Here, if there is no common C-RNTI, it is only needed that the eNB 200selects an eNB to be excluded from the CoMP cooperating set based on themeasurement report from the UE 100 and a common C-RNTI is selected amongC-RNTI unused in each of the remaining eNBs.

The eNB 200 determining the new C-RNTI updates the CoMP cooperating setinformation stored in the eNB 200 so that the new C-RNTI is included andalso that the eNB 203 is added to the CoMP cooperating set.

At step S2013, the eNB 200 transmits the updated CoMP cooperating setinformation to the eNB 201 to the eNB 203 over the X2 interface. The eNB201 to the eNB 203 store the updated CoMP cooperating set informationwhen the updated CoMP cooperating set information is received.

At step S2014, the eNB 200 to the eNB 203 transmit the updated CoMPcooperating set information to the UE 100. The UE 100 recognizes thatthe changed C-RNTI contained in the updated CoMP cooperating setinformation is allocated and uses the changed C-RNTI hereinafter.

At step S2015, the eNB 200 receives packet data from the S-GW.

At step S2016, the eNB 200 transfers the PDCP PDU to the eNB 201 to theeNB 203 over the X2 interface.

At step S2017, each of the eNB 200 to the eNB 203 transmits/receivesband allocation information on an allocation candidate band to/fromanother eNB included in the CoMP cooperating set over the X2 interfaceand determines a band to be allocated to the UE 100.

At step S2018, each of the eNB 200 to the eNB 202 allocates the banddetermined at step S2017 to the UE 100 and transmits the same data tothe UE 100.

Although an example in which the eNB 203 is using the same RNTI (alreadyallocated) is described in the present sequence, but if the eNB 203 isnot using the same C-RNTI, step S2010 to step S2012 are not performed.

In this manner, the eNB 200 transmits C-RNTI which is being used for theCoMP communication with the UE 100 to the eNB 203 which is not includedin the CoMP cooperating set with the C-RNTI being contained in the CoMPadding request. The eNB 203 notifies the eNB 200 whether the C-RNTIcontained in the CoMP adding request is being used after the CoMP addingrequest from the eNB 200 is received. The eNB 200 request the eNB 201 tothe eNB 203 to give notice of the unused C-RNTI if the eNB 203 is usingthe same C-RNTI. The eNB 201 to the eNB 203 notifies the eNB 200 of theC-RNTI unused in the eNB itself in response to the request from the eNB200. The eNB 200 determines a new C-RNTI which is a common C-RNTI amongthe C-RNTI unused in the eNB 200 to the eNB 203 is used for the CoMPcommunication in response to the notification from the eNB 201 to theeNB203. Accordingly, the eNB 203 which has been already using the C-RNTIto be used for the CoMP cooperating set can be added to the CoMPcooperating set.

The eNB 200 notifies another eNB included in the CoMP cooperating set ofthe C-RNTI to be newly used after determining the newly-used C-RNTI.Accordingly, even if C-RNTI is changed during the CoMP communication,each eNB included in the CoMP cooperating set can know the new C-RNTI.

(6.3.2) eNB Adding Pattern 2

FIG. 19 illustrates a pattern 2 of an eNB adding sequence. An initialstate of the present pattern is same as the above-described operationpattern 1. In addition, step S2101 to step S2105 in FIG. 19 are same asthe above-described step S2001 to step S2005. Thus, the descriptionthereof is omitted.

As illustrated in FIG. 19, at step S2106, the eNB 200 determines basedon the measurement report that the eNB 203 is added to the CoMPcooperating set.

At step S2107, the eNB 200 transmits a CoMP adding request forrequesting to be added to the CoMP cooperating set over the X2interface. The eNB 200 transmits C-RNTI which is being used for the CoMPcommunication with the UE 100 with the C-RNTI contained in the CoMPadding request.

At step S2108, the eNB 203 determines based on the CoMP adding requestreceived from the eNB 200 if C-RNTI same as the C-RNTI which is beingused in the CoMP cooperating set to which the eNB 200 belongs is used.Then, the eNB 203 changes the same C-RNTI to another C-RNTI when it isdetermined that the same C-RNTI is being used.

At step S2109, the eNB 203 transmits, to the eNB 200, a CoMP addingresponse which is a response to the CoMP adding request over the X2interface.

The eNB 200 having received the CoMP adding request updates the CoMPcooperating set stored in the eNB 200 so that the eNB 203 is added tothe CoMP cooperating set.

At step S2110, the eNB 200 transmits the updated CoMP cooperating setinformation to the eNB 201 to the eNB 203 over the X2 interface. The eNB201 to the eNB 203 store the updated CoMP cooperating set informationwhen the updated CoMP cooperating set information is received.

At step S2111, the eNB 200 to the eNB 203 transmit the updated CoMPcooperating set information to the UE 100.

The sequence hereinafter is same as the above-described pattern 1.

In this manner, the eNB 200 transmits C-RNTI which is being used for theCoMP communication with the UE 100 to the eNB 203 which is not includedin the CoMP cooperating set with the C-RNTI being contained in the CoMPadding request. The eNB 203 changes the same C-RNTI to another C-RNTI ina case where the C-RNTI same as the C-RNTI contained in the CoMP addingrequest us being used when the CoMP adding request from the eNB 200 isreceived. Accordingly, the eNB 203 which has been already using theC-RNTI to be used for the CoMP cooperating set can be added to the CoMPcooperating set.

(7) CoMP Communication Control

Hereinafter, CoMP communication control is described in the order of(7.1) E-PDCCH, (7.2) Band Allocation Control and Timing Advance Control,and (7.3) Data Synchronization and Retransmission Control.

(7.1) E-PDCCH

In general, UE receives downlink control information (DCI) which istransmitted from eNB on PDCCH and performs communication based on SI(Scheduling Information) or the like which is resource allocationinformation contained in the DCI. Here, a time-frequency resource (PDCCHresource) to be used as PDCCH changes according to a communication statebetween eNB and UE.

However, if a CoMP cooperating set is formed by different eNBs, each eNBincluded in the CoMP cooperating set individually performs PDCCHresource allocation to the UE. Thus, it is difficult to allocate thesame PDCCH resource to the UE and apply JT type CoMP to the PDCCH domain(control domain). Also, when each eNB included in the CoMP cooperatingset allocates the PDCCH resource to the UE, the consumption of the PDCCHresource is large. For these reasons, the present embodiment uses thefollowing configuration to properly transmit DCI even when the CoMPcommunication is performed.

The LTE system 1 according to the present embodiment performscommunication using the downlink frame configuration including thecontrol domain for transmitting DCI and the data domain for transmittingdownlink user data. Each of the plurality of eNBs performing the CoMPcommunication with the UE comprises a transmission unit (the processor241 and the radio transceiver 220) that transmits the DCI by using thedate domain in place of the control domain, when the CoMP communicationis performed with the UE.

Note that DCI contains uplink SI (Scheduling Information) and downlinkSI. Furthermore, the DCI may contain additional information for theCoMP. The uplink SI indicates an uplink allocation resource block and anallocation MCS. The downlink SI indicates a downlink allocation resourceblock and an allocation MCS.

FIG. 20 illustrates a downlink sub-frame configuration.

As illustrated in FIG. 20, the downlink sub-frame includes twocontinuous downlink slots. A section of maximum 3 (or 4) OFDM symbolsfrom the head of the first half slots within the downlink sub-frame is acontrol domain including time-frequency resources to be mainly used asPDCCH. The remaining OFDM symbol section of the downlink sub-frame is adata domain including time-frequency resources to be mainly used asPDSCH.

In the present embodiment, the eNB transmits DCI in the data domain inplace of the control domain when CoMP communication with the UE isperformed. Also, the eNB transmits DCI using a specific resource block(RB) in the data domain when the DCI is transmitted in the data domain.In this manner, the specific resource block in the data domain is usedfor transmitting the DCI as similar to the PDCCH.

Such new PDCCH is referred to as “E-PDCCH (Evolved-PDCCH)”. As describedabove, each eNB included in the CoMP cooperating set uses same resourceblock as the E-PDCCH. In the present embodiment, the resource block tobe used as the E-PDCCH is determined by an anchor eNB.

However, the DCI is originally information to notify the UE of aresource block allocated to the data domain. Thus, if the DCI istransmitted in the data domain, the UE cannot be notified of theresource block allocated to the data domain.

For this reason, the eNB transmits information indicating the resourceblock to be used as the E-PDCCH by broadcasting. For example,information indicating the resource block used as the E-PDCCH can beincluded in a system information block (SIB) which is mapped in 6resource blocks in the center of the downlink bandwidth.

Instead, when notifying the UE of the CoMP cooperating set information,the eNB may notify the UE of the information indicating the resourceblock (fixed) used as the E-PDCCH, which is included in the CoMPcooperating set information.

Furthermore, since a data amount of the DCI is smaller than that of userdata, transmission of DCI only for one UE in one resource block leads toa waste of resource. For this reason, the eNB allocates one resourceblock for the plurality of UEs for the E-PDCCH and performs codedivision multiplex by coding multiple DICs for the plurality of UEs withdifferent spread codes. Accordingly, a resource utilization efficiencycan be improved.

On the other hand, the UE receives the SIB or the CoMP cooperating setinformation to specify the resource block for the E-PDCCH allocated tothe UE itself and thereafter receives DCI transmitted by the E-PDCCH.Here, the DCI is coded with the spread code for the UE. The UE can bealso notified of the spread code for the UE through the SIB or the CoMPcooperating set information, as similar to the allocation information ofthe E-PDCCH.

The UE comprises a receiver (the radio transceiver 120) that receivesthe coded DCI and a decoder (the processor 131) that decodes the DCIreceived by the receiver by using a spread code for the UE itself, andwhen the decoding succeeds, the decoder recognizes the decoded DCI asDCI addressed to the UE itself.

As described above, each of the plurality of eNBs performing the CoMPcommunication with the UE transmits the DCI in the data domain in placeof the control domain when the CoMP communication with the UE areperformed, so that the DCI can be properly transmitted even when theCoMP communication is performed.

(7.2) Band Allocation Control and Timing Advance Control

(7.2.1) Band Allocation Control

As described above, when the CoMP cooperating set is formed by differenteNBs, a band to be allocated to the UE has to be determined bynegotiation among the eNBs. Here, the band means a frequency resource (aresource block), a time resource (sub-frame), and a modulation scheme(MCS). In addition, the band is not a band for the DCI (a band of theE-PDCCH) but a band for transmitting user data (a band of PDSCH and/or aband of PUSCH).

If negotiation between eNBs requires a long time due to the transmissiondelay between the eNBs, a proper band allocation cannot be performed.For this reason, in the present embodiment, the following configurationis used to shorten time required for determining a band to be allocatedto the UE in the CoMP.

In the present embodiment, each of a plurality of eNBs included in theCoMP cooperating set comprises a notification unit (the networkcommunication unit 230 and the processor 241) that notifies other eNBsincluded in the CoMP cooperating set of an allocation candidate band forUE in the eNB itself, a receiver (the network communication unit 230)that receives a notification of an allocation candidate band for the UEin the other eNB from the other eNB included in the CoMP cooperatingset, and a selector (the processor 241) that selects a band to beallocated to the UE from allocation candidate bands in the plurality ofeNBs, based on the notification received by the receiver.

The selector selects a band to be allocated to the UE from allocationcandidate bands in the plurality of eNBs, according to a selection rulecommon to the plurality of eNBs. In this manner, each eNB included inthe CoMP cooperating set notifies other eNBs of an allocation candidateband to the other eNBs and selects a band to be allocated to the UE,according to the predetermined selection rules, from these allocationcandidate bands. Accordingly, the band can be determined only byone-sided notification. Thus, time required for determining a band canbe shortened.

As the common selection rule, any of the following selection rules 1, 2can be used.

Selection rule 1: The notification unit creates a timing advance valueto adjust transmission timing of UE and notifies the other eNBs includedin the CoMP cooperating set of the created timing advance value. Thereceiver receives a timing advance value created in other eNBs includedin the CoMP cooperating set from the other eNBs. In the selection rule1, the common selections rule is a rule that an allocation candidateband in the eNB that creates a timing advance value causing the longestdelay in the transmission timing of UE (i.e., the smallest timingadvance value) among the plurality of eNBs is selected as a band to beallocated to the UE. The timing advance value causing the longest delayin the transmission timing of UE is selected as a timing advance valuethat the UE is to be notified, as described later. Accordingly, theselection rule 1 is a selection rule based on a timing advance value.

Selection rule 2: The notification unit selects MCS to be applied by theeNB to the UE and notifies other eNBs included in the CoMP cooperatingset of the selected MCS. The receiver receives the MCS between the othereNB included in the CoMP cooperating set and the UE from the other eNB.In the selection rule 2, the common selection rule is a rule that anallocation candidate band in the eNB having selected the MCS whosetransmission rate is the highest (i.e., MCS with low error resistance)among a plurality of eNBs is selected as a band to be allocated to theUE. The CoMP communication is expected to improve the UE communicationquality, and thus a UE throughput can be increased by selecting the MCSwhose transmission rate is high.

Furthermore, a selection rule may be a selection rule that an allocationcandidate band in eNB whose number of resource block of the allocationcandidate is the smallest among the plurality of eNBs can be selected asa band to be allocated to the UE.

FIG. 21 illustrates a state where each eNB included in a CoMPcooperating set notifies other eNBs of an allocation candidate band.

As illustrated in FIG. 21, each of the eNB 200 to the eNB 204 includedin the CoMP cooperating set transmits band allocation informationindicating the allocation candidate band to all eNBs other than the eNBitself in the CoMP cooperating set over the X2 interface. Each of theeNB 200 to the eNB 204 receives the band allocation information from allthe eNBs other than the eNB in the CoMP cooperating set. Then, each ofthe eNB 200 to the eNB 204 selects a band to be allocated to the UEamong the allocation candidate band in the eNB and the allocationcandidate bands in the other eNBs according to the above-describedselection rules.

FIG. 22 shows an example of band allocation information.

As illustrated in FIG. 22, the band allocation information includes anidentifier of UE to be a target, an identifier of transmission sourceeNB, an allocation candidate time (transmission scheduling time), anallocation candidate resource block, an allocation candidate modulationscheme (MCS), an identifier of transmission target data, and a timingadvance value.

The identifier of UE to be a target is the above-described C-RNTI. Theidentifier of transmission source eNB is an identifier of eNB havingtransmitted the band allocation information. The allocation candidatetime (timing) indicates a sub-frame of the allocation candidate in thetransmission source eNB and is expressed by, for example, a sub-framenumber. Instead, the allocation candidate time (timing) is expressed bySFN+sub-frame number. The allocation candidate resource block indicatesa resource block of the allocation candidate in the transmission sourceeNB and is expressed by, for example, a resource block number.

The identifier of the transmission target data is for securing identify(for synchronization) of transmission data between eNBs and is asequence number of PDCD PDU in the present embodiment. The sequencenumber of the PDCD PDU is added by an anchor eNB. The detail ofprocessing of adding the sequence number to the PDCD PDU is describedlater.

The timing advance value is a timing advance value created in thetransmission source eNB.

FIG. 23 illustrates one example of the band allocation processing in theeNB included in the CoMP cooperating set.

As illustrated in FIG. 23, at step S300, the eNB checks if the UE is aCoMP target. If the UE is the CoMP target (step S300; Yes), processingproceeds to step S303, and if not (step S300; No), processing proceedsto step S301.

At step S301, the eNB performs calculation for determining a band to beallocated to the UE. As for UE which is not a target for CoMP, based onCQI and/or SRS transmitted from the UE, an allocation band is determinedaccording to a regular scheduling algorithm such as proportionalfairness (PF).

At step S302, the eNB transmits DCI indicating the band determined atstep S301 to the UE on the PDCCH.

On the other hand, at step S303, the eNB secures a reserved band(allocation candidate band) of the UE for CoMP in order to prioritizethe band allocation to the UE which is a target for CoMP.

At step S304, the eNB stores the result at step S303.

At step S305, the eNB transmits the band allocation information (seeFIG. 22) indicating the band secured for the UE at step S302 (i.e., theallocation candidate band) to another eNB included in the CoMPcooperating set which performs the CoMP communication with the UE overthe X2 interface.

At step S306, the eNB activates a timer to time until the timing of theband allocation determination processing.

FIG. 24 shows an example of band allocation determination processing.

As illustrated in FIG. 24, at step S400, the eNB checks if the timeractivated at step S306 expires. If the timer expires (step S400; Yes),processing proceeds to step S401.

At step S401, the eNB checks if band allocation information from all theother eNBs included in the CoMP cooperating set which performs CoMPcommunication with the UE is received. If the band allocationinformation is received from all the other eNBs (step S401; Yes),processing proceeds to step S404, and if not (step S401; No), processingproceeds to step S402.

At step S404, the eNB determines an allocation band to the UE from theallocation candidate band stored at step S304 and the allocationcandidate bands for the other eNBs included in the CoMP cooperating setaccording to the above-described selection rules.

At step S405, the eNB transmits DCI indicating the allocation banddetermined at step S404 to the UE on the E-PDCCH and also transmits (orreceives) the user data to (or from) the UE using the allocation band.

On the other hand, at step S402, the eNB times out without receiving theband allocation information from at least one of the other eNBs includedin the CoMP cooperating set. The eNB determines a band from theallocation candidate band stored at step S304 and the allocationcandidate band indicated by the received band allocation informationaccording to the above-described selection rules. Here, since the bandallocation information is not received from at least one of the othereNBs included in the CoMP cooperating set, a band different from theband to be used in common in the CoMP cooperating set might be selected.

At step S403, the eNB reserves the band determined at step S402 as anallocation-disabled band and stops transmission (or reception) of userdata using the band. This can prevent adverse effects of datatransmission (or reception) in the band different from the band to beused in common n the CoMP cooperating set.

FIG. 25 illustrates a JT-type CoMP sequence. Here, the description isgiven to an example in which the CoMP cooperating set formed by the eNB200 to the eNB 204 and the UE 100 are executing the JT type CoMP and theeNB 204 operates as an anchor eNB.

As illustrated in FIG. 25, at step S3001, the eNB 204 operating as ananchor eNB receives packet data (user data) from the S-GW.

At step S3002, the eNB 204 converts the packet data in the PDCP layer toPDCP PDU with a sequence number and transfers the PDCP PDU to the eNB200 to the eNB 203 over the X2 interface.

At step S3003, the eNB 204 creates band allocation information 1 andtransfers the created band allocation information 1 to the eNB 200 tothe eNB 203 over the X2 interface.

At step S3004, the eNB 203 creates band allocation information 2 andtransfers the created band allocation information 2 to the eNB 200, eNB201, eNB 202 and eNB 204 over the X2 interface.

At step S3005, the eNB 202 creates band allocation information 3 andtransfers the created band allocation information 3 to the eNB 200, eNB201, eNB 203 and eNB 204 over the X2 interface.

At step S3006, the eNB 201 creates band allocation information 4 andtransfers the created band allocation information 4 to the eNB 200, eNB202, eNB 203 and eNB 204 over the X2 interface.

At step S3007, the eNB 200 creates band allocation information 5 andtransfers the created band allocation information 5 to the eNB 201 tothe eNB 204 over the X2 interface.

At step S3008, each of the eNB 200 to the eNB 204 determines a band tobe allocated to the UE 100 based on the band allocation information ofthe eNB itself and the band allocation information from the other eNBs.

At step S3009, each of the eNB 200 to the eNB 204 transmits the userdata to the UE 100 in the allocation band determined at step S3008.

As described above, each eNB included in the CoMP cooperating setnotifies other eNBs of an allocation candidate band and selects a bandto be allocated to the UE according to the predetermined selection ruleamong these allocation candidate bands. Thus, time required fordetermining the band can be shortened.

Also, in the present embodiment, each of a plurality of eNBs has anotification unit (the network communication unit 230 and the processor241) that notifies other eNBs included in the CoMP cooperating set of anallocation candidate band for UE in the eNB itself, a receiver (thenetwork communication unit 230) that receives a notification of theallocation candidate band for the UE in the other eNB from the other eNBincluded in the CoMP cooperating set, and a disabling unit (theprocessor 241) that performs setting to disable allocation of allocationcandidate band depending on a reception state of the receiver. When thereceiver does not receive the notification from at least one of theother eNBs included in the CoMP cooperating set, the disabling unitperforms setting to disable the allocation of the allocation candidateband recognized by the eNB itself among the allocation candidate bandsin the plurality of eNBs. Each of the plurality of eNBs furthercomprises a selector (the processor 241) selects a band to be allocatedto the UE among the allocation candidate bands in the plurality of eNBsaccording to the selection rule common to the plurality of eNBs. Thedisabling unit performs setting to disable allocation of the allocationcandidate band selected according to the selection rule.

Accordingly, when the band allocation information istransmitted/received between the base stations included in the CoMPcooperating set, part of eNBs in the CoMP cooperating set is preventedfrom performing wrong allocation to the UE, even though the bandallocation information is not normally transmitted/received due tocongestion between the eNBs.

(7.2.2) Timing Advance Control

When a plurality of eNBs receive same data from UE n the JR-type CoMP, aproper timing advance value differs depends on each eNB. For thisreason, it is difficult that the timing advance value is properly set.For this reason, in the present embodiment, the following configurationis used to properly set the timing advance value.

In the present embodiment, each of the eNBs included in the CoMPcooperating set comprises a transmission unit (the processor 241 and thenetwork communication unit 230) that creates a timing advance value foradjusting data transmission timing of UE and transmits the createdtiming advance value to other eNBs included in the CoMP cooperating set,a receiver (the network communication unit 230) that receives a timingadvance value created in the other eNB from the other eNB included inthe CoMP cooperating set, and a notification unit (the processor 241 andthe radio transceiver 220) that notifies the UE of the timing advancevalue selected among the timing advance values in the plurality of eNBsbased on the notification received by the receiver. In the presentembodiment, a timing advance value causing the longest delay in the datatransmission timing among the timing advance values in the plurality ofeNBs is selected.

As described above, in the LTE system 1, CP is provided for each symbolso as to handle a delayed wave. Thus, the eNB can demodulate even anuplink signal (uplink data) which arrives with a delay from thereception timing of the eNB if the delay is within a range of a CPlength. On the other hand, it is difficult to demodulate an uplinksignal which arrives earlier than the reception timing of the eNB. Forthis reason, the timing advance value causing the longest delay inuplink transmission timing is selected, so that the timing advance valuecan be properly set.

In the present embodiment, the band allocation information which istransmitted/received by each eNB (see, FIG. 22) includes a timingadvance value. Accordingly, the timing advance value can be alsoselected in the above-described band allocation determinationprocessing.

For example, at step S404 in FIG. 24, the eNB determines a timingadvance value that the UE is to be notified of according to the timingadvance value selection rule of a timing advance value created by theeNB itself and timing advance values of the respective other eNBsincluded in the CoMP cooperating set. Accordingly, the timing advancevalue can be determined only by one-direction notification. Thus, timerequired for determining a timing advance value can be shortened.

Then, at step S405, the eNB transmits the timing advance valuedetermined at step S404 to the UE on PDSCH. Here, if the PDSCH resourceto be allocated to the UE has free space, the eNB notifies the UE of thetiming advance value (TA MCE) using the free space of the PDSCHresource. The case where there is the PDSCH resource has free spacemeans that a bandwidth for transmission using the selected resourceblock and the selected MCS is larger than the data to be transmitted.

Note that if the JT-type CoMP is performed, all eNBs included in theCoMP cooperating set have to transmit downlink data in the same band.However, at timing when there is no downlink data to be cooperativelytransmitted, all the eNBs included in the CoMP cooperating set maycooperatively transmit the timing advance value (TA MCE) or only ananchor eNB may transmit the timing advance value (TA MCE).

However, each eNB included in the CoMP cooperating set is not alwaysobtained the timing advance value from all the other eNBs included inthe CoMP cooperating set. Thus, the timing advance value is held foreach of the other eNBs and is updated every time a new timing advancevalue is received. Specifically, each eNB included in the CoMPcooperating set further comprises a storage (the memory 242) for storingthe timing advance value received by the receiver (the networkcommunication unit 230) and an update unit (the processor 241) thatupdates the timing advance value stored in the storage with the receivedtiming advance value every time the receiver receives the timing advancevalue. The notification unit (the processor 241 and the radiotransceiver 220) selects the timing advance value that the UE is to benotified of among the timing advance values stored in the storage andnotifies the UE of the selected timing advance value.

Also, the UE has to be notified of the timing advance value before TimeAlignment Timer (first timer) of UE expires. In addition, each eNBincludes a Time Alignment Timer corresponding to the Time AlignmentTimer of UE. In the case of performing the JT-type CoMP, if detectingthat the Time Alignment Timer of UE will expire soon, an anchor eNB maytransmit a timing advance value (TA MCE) as user data, as similar toother downlink data, to the other eNBs included in the CoMP cooperatingset over the X2 interface, and all the cooperating eNBs may transmit thetiming advance value cooperatively as similar to other downlink data.

(7.2.3) Abnormal Time Sequence

(7.2.3.1) Pattern 1

In a case where transmission/reception timeout of the band allocationinformation occurs frequently (or continues) between specific eNBs,congestion may be occurring on a communication path between the specificeNBs. In the present embodiment, the following configuration is used toproperly address the above-described case.

In the present embodiment, each of the plurality of eNBs included in theCoMP cooperating set comprises a receiver (the network communicationunit 230) that receives information on resource allocation to the UE inother eNB included in the CoMP cooperating set from the other eNB and areporting unit (the processor 241 and the network communication unit230) that reports the information on another specific eNB included inthe CoMP cooperating set to the CoMP management apparatus (the anchoreNB) managing the CoMP cooperating set when the receiver does notnormally receive the notification from the other specific eNB. The CoMPmanagement apparatus excludes the other specific eNB and/or thereporting eNB from the CoMP cooperating set. For example, the CoMPmanagement apparatus acquires a power level of a signal received by theUE from the other specific eNB and a power level of a signal received bythe UE from the reporting eNB and excludes, from the CoMP cooperatingset, one of the other specific eNB and the reporting eNB whosecorresponding power level is lower than that of the other eNB.

FIG. 26 illustrates a JT-type CoMP sequence. Here, the description isgiven to an example in which the CoMP cooperating set formed by the eNB200 to the eNB 204 and the UE 100 are executing the JT type CoMP and theeNB 204 operates as an anchor eNB.

As illustrated in FIG. 26, at step S3101, the eNB 204 operating as ananchor eNB receives packet data (user data) from the S-GW.

At step S3102, the eNB 204 converts the packet data in the PDCP layer toPDCP PDU with a sequence number and transfers the PDCP PDU to the eNB200 to the eNB 203 over the X2 interface.

At step S3103, the eNB 204 creates band allocation information 1 andtransfers the created band allocation information 1 to the eNB 200 tothe eNB 203 over the X2 interface.

At step S3104, the eNB 203 creates band allocation information 2 andtransfers the created band allocation information 2 to the eNB 200, eNB201, eNB 202 and eNB 204 over the X2 interface. Here, it is assumed thatthe band allocation information 2 from the eNB 203 does not reach theeNB 201 within a predetermined time period.

At step S3105, the eNB 202 creates band allocation information 3 andtransfers the created band allocation information 3 to the eNB 200, eNB201, eNB 203 and eNB 204 over the X2 interface.

At step S3106, the eNB 201 creates band allocation information 4 andtransfers the created band allocation information 4 to the eNB 200, eNB202, eNB 203 and eNB 204 over the X2 interface.

At step S3107, the eNB 200 creates band allocation information 5 andtransfers the created band allocation information 5 to the eNB 201 tothe eNB 204 over the X2 interface.

At step S3108, each of the eNB 200 to the eNB 204 determines a band tobe allocated to the UE 100 based on the band allocation information ofthe eNB itself and the band allocation information from the other eNBs.However, since the band allocation information 2 from the eNB 203 doesnot arrive within the predetermined time period, the eNB 201 determinesthe above-described allocation-disabled band.

At step S3109, the eNB 201 transmits band allocation receptioninformation indicating that the band allocation information from the eNB203 is not received to the eNB 204 over the X2 interface. The bandallocation reception information includes an identifier of eNB 201 (or acell identifier) and an identifier of the eNB 203 (or a cellidentifier).

At step S3110, each of the eNB 200, eNB 202, eNB 203, and eNB 204transmits the user data to the UE 100 in the allocation band determinedat step S3108.

At step S3111, the eNB 204 determines an eNB to be excluded from theCoMP cooperating set based on the band allocation information receivedat step S3109. For example, the eNB 204 acquires a power level of asignal received by the UE 100 from the eNB 201 and a power level whichis received by the UE 100 from the eNB 203 and excludes one of the eNB201 and eNB 203 whose corresponding power level is lower than that ofthe other eNB, from the CoMP cooperating set. The eNB excluded from theCoMP cooperating set may be an interference source for the CoMPcommunication thereafter. Thus, an eNB whose interference level to begiven to the UE 100 is expected to be small is excluded. Here, it isassumed that the eNB 204 determines to exclude the eNB 201. The eNB 204updates the CoMP cooperating set information so as to reflect theexclusion of the eNB 201 when it is determined that the eNB 201 isexcluded.

At step S3112, the eNB 204 transmits the updated CoMP cooperating setinformation to the eNB 200 to the eNB 203 (and the UE 100). The eNB 201having received the updated CoMP cooperating set information recognizesthat the eNB 201 is excluded from the CoMP cooperating set and does notjoin the CoMP communication thereafter.

As described above, according to the present embodiment, properprocessing can be performed even when a transmission/reception timeoutof the band allocation information frequently occurs (or continues)between specific eNBs. Note that in the present sequence, the JT-typeCoMP is described as an example. However, the sequence can be applied toother CoMP types such as JR type CoMP.

(7.2.3.2) Pattern 2

In the JR-type CoMP, the specific eNB which does not receive the bandallocation information from the other eNB determines theallocation-disabled band and does not receive the uplink data from theUE 100 as described above. In this case, the anchor eNB waits for datatransfer from the specific eNB although the specific eNB does notreceive the uplink data.

For this reason, in the present embodiment, the following configurationis used in order to properly address the case where any of the eNBs donot receive data from the UE in the JR-type CoMP.

In the present embodiment, each of the plurality of eNBs included in theCoMP cooperating set comprises a band allocation information receiver(the network communication unit 230) that receives the band allocationinformation indicating a communication resource of allocation candidatefor the UE in another eNB included in the CoMP cooperating set from theother eNB, and a transmission unit (the processor 241 and the networkcommunication unit 230) that transmits information on whether thereception of the band allocation information succeeds to another eNB(the anchor eNB) included in the CoMP cooperating set based on areception state in the band allocation information receiver. When theband allocation information receiver does not receive band allocationinformation from at least one of other eNBs included in the CoMPcooperating set, the transmission unit transmits error information tothe other eNB (the anchor eNB) included in the CoMP cooperating set. Onthe other hand, when the band allocation information receiver receivesthe band allocation information from the other eNBs included in the CoMPcooperating set, the transmission unit transmits acknowledgementinformation to the other eNB (the anchor eNB).

Also, each of the plurality of eNBs further comprises a datatransmission unit (the radio transceiver 220 and the processor 241) thatreceives data from the UE based on the band allocation informationreceived by the band allocation information receiver. When the bandallocation information receiver does not receive the band allocationinformation from at least one of the other eNBs included in the CoMPcooperating set, the data receiver stops the data reception from the UE.

FIG. 27 illustrates a JR-type CoMP sequence. Here, the description isgiven to an example in which the UE 100 and the CoMP cooperating setformed by the eNB 200 to the eNB 203 are executing the JR type CoMP andthe eNB 200 operates as an anchor eNB.

As illustrated in FIG. 27, at step S3201, the eNB 203 creates bandallocation information 1 and transfers the created band allocationinformation 1 to the eNB 200 to the eNB 202 over the X2 interface.

At step S3202, the eNB 202 creates band allocation information 2 andtransfers the created band allocation information 2 to the eNB 200, eNB201, and eNB 203 over the X2 interface. Here, it is assumed that theband allocation information 2 from the eNB 202 to the eNB 201 does notreach within a predetermined time period.

At step S3203, the eNB 201 creates band allocation information 3 andtransfers the created band allocation information 3 to the eNB 200, eNB202, and eNB 203 over the X2 interface.

At step S3204, the eNB 200 creates band allocation information 4 andtransfers the created band allocation information 4 to the eNB 201 tothe eNB 203 over the X2 interface.

At step S3205, the eNB 203 transmits band allocation receptioninformation indicating that the eNB 203 received all the band allocationinformation with a predetermined time period to the eNB 200 over the X2interface. The band allocation reception information includes anidentifier of a transmission source eNB (or a cell identifier).

At step S3206, the eNB 202 transmits band allocation receptioninformation (ACK) indicating that the eNB 202 received all the bandallocation information within a predetermined time period to the eNB 200over the X2 interface.

At step S3207, the eNB 201 transmits band allocation receptioninformation (NACK) indicating that the eNB 201 did not receive at leastone piece of the band allocation information within the predeterminedtime period (and/or stops the reception of the uplink data) to the eNB200 over the X2 interface.

At step S3208, each of the eNB 200 to the eNB 203 determines a band tobe allocated to the UE 100 based on the band allocation information ofthe eNB itself and the band allocation information from the other eNBs.However, since the band allocation information 2 from the eNB 202 hasnot reached within the predetermined time period, the eNB 202 determinesthe allocation-disabled band as described above. The UE 100 is notifiedof the allocation band determined at step S3208 over the E-PDCCH.

At step S3209, the UE 100 transmits uplink data using the allocationband. Each of the eNB 200, the eNB 202, and the eNB 203 receives theuplink data. On the other hand, the eNB 201 does not receive the uplinkdata (step S3210).

At step S3211, the eNB 203 transfers the uplink data received from theUE 100 with the data being in a state of a baseband signal (a statebefore decoding) to the eNB 200 over the X2 interface.

At step S3212, the eNB 202 transfers the uplink data received from theUE 100 with the data being in a state of a baseband signal (a statebefore decoding) to the eNB 200 over the X2 interface.

Note that the eNB 200 recognizes that there is no data transfer from theeNB 201 based on the band allocation reception information (NACK)received at step S3207.

At step S3213, the eNB 200 decodes the uplink data received by the eNBitself from the UE 100, the uplink data transferred from the eNB 202,and the uplink data transferred from the eNB 201 after the uplink databeing combined.

At step S3214, the eNB 200 transfers the data after decoding with thedata being in a state of IP packet to the S-GW on the S1 interface.

As described above, according to the present embodiment, the anchor eNBcan be prevented from waiting for the data transfer from a specific eNBunder the condition in which the specific eNB has not received uplinkdata. Thus, an increase in communication delay can be avoided.

(7.3) Data Synchronization and Retransmission Control

Hereinafter, data synchronization and retransmission control in theJT-type CoMP are described.

(7.3.1) Data Synchronization and ARQ Retransmission

In the JT-type CoMP, when the CoMP cooperating set is formed bydifferent eNBs, there is a following problem. In a layer 2 of each eNBincluded in the CoMP cooperating set, when user data is converted toPDCP PDU in a PDCP layer, and thereafter ARQ in an AM mode is executedin a RLC layer, the eNBs perform data division differently from eachother in the RLC layer (see, FIG. 5 and FIG. 6). As a result, it isdifficult for the eNBs to transmit same data to the UE at the same time.

For this reason, the present embodiment uses the following configurationin order to cause each eNBs to transmit same data to the UE at the sametime even when the CoMP cooperating set is formed by the different eNBs.

In the present embodiment, an anchor eNB has a receiver (the networkcommunication unit 230) that receives user data addressed to UE from anS-GW, a conversion unit (the processor 241) that converts the user datareceived by the receiver to PDCP PDU to which a sequence number is addedin the PDCP layer, and a transmission unit (the network communicationunit 230 and the processor 241) that transmits the PDCP PDU obtained bythe conversion unit to another eNB (subordinate eNB) included in theCoMP cooperating set. When receiving the PDCP PDU, the other eNB(subordinate eNB) processes the PDCP PDU in the MAC layer withoutapplying ARQ retransmission in the RLC layer. For example, a UM mode isapplied to the RLC layer in the other eNB (subordinate eNB). Theprocessing in the MAC layer includes HARQ (see, FIG. 5).

Also, in the present embodiment, the subordinate eNB comprises atransmission unit (the radio transceiver 220 and the processor 241) thatperforms HARQ data transmission to the UE and a notification unit (thenetwork communication unit 230 and the processor 241) that notifies theanchor eNB of a failure of the HARQ data transmission when the HARQ datatransmission fails. The anchor eNB has a management unit (the processor241 and the memory 242) that collectively manages ARQ retransmissiondata (PDCP PDU) from the CoMP cooperating set to the UE, a receiver (thenetwork communication unit 230) that receives a notification of thefailure of the HARQ data transmission from the subordinate eNB, and atransfer unit (the network communication unit 230 and the memory 242)that transfers the ARQ retransmission data which is managed by themanagement unit to the subordinate eNB in response to the notificationreceived by the receiver. The transmission unit of the subordinate eNBtransmits ARQ retransmission data transferred from the anchor eNB to theUE using the HARQ.

FIG. 28 illustrates a JT-type CoMP sequence. Here, the description isgiven to an example in which the UE 100 and the CoMP cooperating setformed by the eNB 200 to the eNB 204 are executing the JT type CoMP andthe eNB 200 operates as an anchor eNB.

As illustrated in FIG. 28, at step S4001, the S-GW transmits user dataaddressed to the UE 100 to the eNB 200 on the S1 interface.

The PDCP layer of the eNB 200 performs header compression/encryption ofthe user data addressed to the UE 100 and converts the resultant data toPDCP PDU (see FIG. 5 and FIG. 6). In addition, the PDCP layer of the eNB200 adds a sequence number for identifying the PDCP PDU to the PDCP PDU.Furthermore, the PDCP PDU with a sequence number is stored forretransmission.

At step S4002, the eNB 200 transfers the PDCP PDU with a sequence numberto the eNB 201 to the eNB 204 over the X2 interface.

Then, in the eNB 200 to the eNB 204, the RLC layer performs conversionto PLC PDU without applying ARQ to the PDCP PDU (RLC SDU) with asequence number, and the MAC layer performs conversion to a transportblock by applying HARQ to the RLC PDU (MAC SDU), and the physical layertransmits the transport block. Here, the same band (resource block,sub-frame, MCS) is used for transmission in the physical layer in theeNB 200 to the eNB 204.

Also, each MAC layer of the eNB 200 to the eNB 204 performsretransmission in response to ACK/NACK (HARQ ACK/NACK) from the UE 100.

FIG. 29 illustrates a sequence in a case where HARQ retransmission doesnot complete even when it reaches the maximum retransmission number.

As illustrated in FIG. 29, when the HARQ retransmission dose notterminate even when it reaches the maximum retransmission number (i.e.,in a case where HARQ ACK is not obtained), at step S4011, the eNB 201 tothe eNB 204 notify the eNB 200 of a failure of data transmission overthe X2 interface. The notification contains a sequence number of PDCPPDU having the failure of the data transmission.

At step S4012, the eNB 200 transfers PDCP PDU (with a sequence number)in which ARQ retransmission should be performed in response to thenotification from the eNB 201 to the eNB 204 over the X2 interface.

Then, in the eNB 200 to the eNB 204, the RLC layer performs conversionto PLC PDU without applying ARQ to the PDCP PDU (RLC SDU) with asequence number, and the MAC layer performs conversion to a transportblock by applying HARQ to the RLC PDU (MAC SDU), and the physical layertransmits the transport block. Here, the same band (resource block,sub-frame, MCS) is used for transmission in the physical layer in theeNB 200 to the eNB 204.

As described above, the ARQ retransmission is collectively managed bythe anchor eNB, so that the eNBs included in the CoMP cooperating setcan transmit same data to the UE at the same time in the JT-type CoMP.

(7.3.2.1) HARQ First Transmission Allocation Interval

The eNB repeatedly performs data retransmission by using the HARQ in theMAC layer until ACK (HARQ ACK) from the UE is obtained. Here,transmission processing of first transmission data and retransmissionprocessing for the first transmission data are referred to as “HARQprocess” and a plurality of HARQ processes are executed in parallel.

In the JT-type CoMP, when the CoMP cooperating set is formed bydifferent eNBs, it is considered that negotiation among the eNBs isneeded for allocating the same band for HARQ retransmission to the UE.However, if such negotiation is performed for every retransmission,processing delay for retransmission is so long that the HARQretransmission cannot be properly performed.

For this reason, the present embodiment uses the following configurationto properly perform the HARQ retransmission in the downlink CoMP.

In the present embodiment, each of the plurality of eNBs included in theCoMP cooperating set comprises a first transmission unit (the radiotransceiver 220 and the processor 241) that transmits first transmissiondata in each of the plurality of HARQ processes and a retransmissionunit (the radio transceiver 220, the processor 241 and the memory 242)that transmits retransmission data corresponding to the first data ineach of the plurality of HARQ processes. A transmission interval of thefirst transmission data by the first transmission unit is set to be aminimum odd number larger than a maximum HARQ retransmission number.

Also, a retransmission interval of the retransmission data by theretransmission unit is limited to 8 [TTI (Transmission Time Interval)].In other words, when allocation cannot be performed, a shift to the nextTTI is prohibited. Furthermore, the retransmission unit transmits theretransmission data by applying the resource block and MCS same as thoseof the first transmission data.

FIG. 30 is a drawing for illustrating HARQ retransmission in a MAClayer.

As shown in FIG. 30, each HARQ process performs retransmission by 8[TTI] according to the HARQ NACK from the UE.

On the other hand, the transmission interval of the first transmissiondata is 9[TTI]. In other words, the first transmission interval (9[TTI])is a value in which “1” is added to the retransmission interval(8[TTI]). Thus, the first transmission timing and the retransmissiontiming are not overlapped with each other until the retransmissionnumber turns 8. However, when the retransmission number turns 9, thefirst transmission timing and the retransmission timing are overlappedwith each other. However, the maximum HARQ retransmission number is 8.Thus, the first transmission timing and the retransmission timing arenot overlapped with each other. In the present embodiment, the firsttransmission interval is set to be “9” [TTI] which is the minimum oddnumber larger than the maximum HARQ retransmission number, 8.

By setting as such, the first transmission timing and retransmissiontiming of the HARQ process do not overlap with each other.

Also, in each HARQ process, retransmission is performed using theresource block same as the resource block used at the firsttransmission, and retransmission is also performed using the MCS same asthe MCS used at the first transmission. If such rule is introduced tothe CoMP cooperating set, negotiation among the eNBs for HARQretransmission is unnecessary. Thus, the processing delay forretransmission can be prevented from becoming long.

(7.3.2.2) HARQ ACK

The eNB repeatedly performs data retransmission until ACK from the UE isobtained using the HARQ in the MAC layer. However, if the CoMPcooperating set is formed by different eNBs in the JT-type CoMP, thereis a possibility that any of the eNBs included in the CoMP cooperatingset cannot receive the ACK even when the UE transmits the ACK. The eNBwhich cannot receive the ACK from the UE continues the retransmission tothe UE. Thus, there is a problem that the resource is uselessly consumedby the retransmission.

For this reason, the present embodiment uses the following configurationto properly perform the HARQ retransmission in the downlink CoMP.

In the present embodiment, when receiving the HARQ ACK from the UE, eachof the plurality of eNBs included in the CoMP cooperating set transmitsACK information on the received HARQ ACK to the other eNBs included inthe CoMP cooperating set. The ACK information includes identificationinformation of data corresponding to the HARQ ACK. Each of the pluralityof eNBs performs HARQ retransmission to the UE, if the retransmissiondoes not reach the maximum HARQ retransmission number, if the HARQ ACKfrom the UE is not received and if the ACK information from the othereNBs included in the CoMP cooperating set is not received.

FIG. 31 illustrates a JT-type CoMP sequence. Here, the description isgiven to an example in which the CoMP cooperating set formed by the eNB200 to the eNB 203 and the UE 100 are executing the JT type CoMP and theeNB 200 operates as an anchor eNB.

As illustrated in FIG. 31, at step S4001, the eNB 200 operating as ananchor eNB receives packet data (user data) from the S-GW.

At step S4002, the eNB 200 converts the packet data in the PDCP layer toPDCP PDU with a sequence number and transfers the PDCP PDU to the eNB200 to the eNB 203 over the X2 interface.

At step S4003, each of the eNB 200 to the eNB 203 creates bandallocation information and transfers the created band allocationinformation to another eNB included on the CoMP cooperating set over theX2 interface.

At step S4004, each of the eNB 200 to the eNB 203 transmits same userdata in the same band to the UE 100. Here, it is assumed that thereceived user data is successfully decoded.

At step S4005, the UE 100 transmits HARQ ACK indicating successfuldecoding. The eNB 200 and the eNB 201 receive the HARQ ACK, and the eNB202 and the eNB 203 fail reception of the HARQ ACK.

At step S4006, the eNB 200 and the eNB 201 creates ACK information onthe HARQ ACK from the UE 100 and transfers the created ACK informationto other eNBs included in the CoMP cooperating set over the X2interface. The ACK information includes an identifier of user data(e.g., a PDCP PDU sequence number) and HARQ ACK. FIG. 31 illustrates anexample in which transmission delay of the X2 interface is longer thanthe retransmission interval and the HARQ retransmission is startedbefore receiving the ACK information.

At step S4007, the eNB 202 and the eNB 203 do not receive the HARQ ACK,and thus transmit the retransmission data corresponding to the user datatransmitted at step S4004 to the UE 100. After that, the eNB 200 and theeNB 201 stop retransmission processing when the ACK information isreceived over the X2 interface. Note that, each eNB performs HARQretransmission to the UE if the retransmission does not reach themaximum HARQ retransmission number, if the HARQ ACK from the UE is notreceived and also if the ACK information from the other eNBs included inthe CoMP cooperating set is not received.

As described above, in the present embodiment, when receiving the HARQACK from the UE, the each of the plurality of eNBs included in the CoMPcooperating set transmits ACK information on the received HARQ ACK tothe other eNBs included in the CoMP cooperating set. Accordingly, eventhe eNB which cannot receive the ACK from the UE can stop retransmissionto the UE. Thus, the resource can be prevented from being uselesslyconsumed by the retransmission. If an eNB which does not recognize ACKperforms retransmission using a resource while an eNB having receivedthe ACK allocates the resource to another UE, interference may occur.Thus, the interference can be prevented by the configuration that isenabled to stop the retransmission.

(8) Other Embodiments

As described above, the present disclosure has been described by usingthe above-described embodiments. However, it should not be understoodthat the description and the drawings, which constitute one part of thisdisclosure, are to limit the present disclosure. Various alternativeembodiments, examples, and operational techniques will be obvious forthose who are in the art from this disclosure.

As for the control for the CoMP, the “anchor eNB” described above may beread as “MME” or “S-GW” and at least part of the control executed by theanchor eNB may be executed by an EPC side (MME or S-GW). In this casese, MME or S-GW is equivalent to the CoMP management apparatus whichmanages the CoMP cooperating set.

Also, in the above-described embodiment, the description is given to anexample in which the CoMP cooperating set is formed by a plurality ofeNBs. However, the CoMP cooperating set may include a relay node (RN).The RN is a relay station configuring a backhaul wirelessly and isrecognized by the UE as a cell as similar to the eNB. Also, the CoMPcooperating set may include RRH (Remote Radio Head). The RRH is a radiounit installed spaced apart from the base band unit and connected withthe base band unit via an optical fiber or the like.

In addition, the entire content of U.S. Provisional Application No.61/588,502 (filed on Jan. 19, 2012) and U.S. Provisional Application No.61/598,782 (filed on Feb. 14, 2012) is incorporated in the presentspecification by reference.

INDUSTRIAL APPLICABILITY

As described above, in a mobile communication system, a base station, aCoMP control apparatus, and a communication control method, according tothe present disclosure, in which even when a CoMP cooperating set isformed by different base stations, the base stations can transmit samedata to a user terminal at the same time. Thus, the present disclosureis useful in the field of mobile communications.

The invention claimed is:
 1. A mobile communication system, comprising:a first base station; a second base station connected with the firstbase station via an X2 interface; and a user terminal configured toreceive data from both the first and second base stations using radioresources provided by both the first and second base stations, whereinthe first base station comprises a controller including at least oneprocessor, the controller executing functions of a plurality of layers,the plurality of layers including a packet data convergence protocol(PDCP) layer, a radio link control (RLC) layer, a medium access control(MAC) layer, and a physical (PHY) layer, the controller is configured toreceive user data addressed to the user terminal from a core network,convert the user data to a PDCP data unit provided with a sequencenumber, in the PDCP layer, and transmit the PDCP data unit to the secondbase station from the PDCP layer, wherein the first base station isconfigured to transmit, to the second base station, an addition requestrequesting the second base station to participate in communication withthe user terminal, wherein the addition request includes an identifierallocated by the first base station to the user terminal, and receive anaddition response which is a response for the addition request, from thesecond base station.
 2. The mobile communication system according toclaim 1, wherein the first base station is further configured to receivea measurement report from the user terminal, and determine whether totransmit the addition request on the basis of the measurement report. 3.A first base station connected with a second base station via an X2interface, comprising: a controller including at least one processor andconfigured to communicate with a user terminal, wherein the userterminal receives data from both the first and second base stationsusing radio resources provided by both the first and second basestations, wherein the controller is configured to execute functions of aplurality of layers including a packet data convergence protocol (PDCP)layer, a radio link control (RLC) layer, a medium access control (MAC)layer, and a physical (PHY) layer, the controller is further configuredto receive user data addressed to the user terminal from a core network,convert the user data to PDCP data unit provided with a sequence number,in the PDCP layer, transmit the PDCP data unit to the second basestation from the PDCP layer, transmit, to the second base station, anaddition request requesting the second base station to participate incommunication with the user terminal, wherein the addition requestincludes an identifier allocated by the first base station to the userterminal, and receive an addition response which is a response for theaddition request, from the second base station.
 4. A method for a firstbase station connected with a second base station via an X2 interface,comprising: communicating with a user terminal, wherein the userterminal receives data from both the first and second base stationsusing radio resources provided by both the first and second basestations; executing functions of a plurality of layers including apacket data convergence protocol (PDCP) layer, a radio link control(RLC) layer, a medium access control (MAC) layer, and a physical (PHY)layer; receiving user data addressed to the user terminal from a corenetwork; converting the user data to PDCP data unit provided with asequence number, in the PDCP layer; transmitting the PDCP data unit tothe second base station from the PDCP layer; transmitting, to the secondbase station, an addition request requesting the second base station toparticipate in communication with the user terminal, wherein theaddition request includes an identifier allocated by the first basestation to the user terminal; and receiving an addition response whichis a response for the addition request, from the second base station.